Skip to content

Conversation

@matthiasdiener
Copy link
Contributor

@matthiasdiener matthiasdiener commented Nov 26, 2025

Description

The corresponding 2-stage HIP kernel amax implementation is in #369.

Partially addresses https://github.com/ROCm/frameworks-internal/issues/14303.

See https://github.com/ROCm/frameworks-internal/issues/14303#issuecomment-3554900809 for a performance analysis.

Type of change

  • Documentation change (change only to the documentation, either a fix or a new content)
  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Infra/Build change
  • Code refactoring

Changes

  • Added a 2-stage Triton amax implementation, optional, but enabled by default
    • Disable by setting export NVTE_USE_ATOMIC_AMAX=1 (this will use the previous atomic implementation)

Checklist:

  • I have read and followed the contributing guidelines
  • The functionality is complete
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes

matthiasdiener and others added 30 commits November 12, 2025 14:10
This reverts commit 7d4054e.
@matthiasdiener matthiasdiener self-assigned this Nov 26, 2025
@matthiasdiener matthiasdiener changed the base branch from dev to speedup-amax-kernel November 26, 2025 22:16
@matthiasdiener matthiasdiener changed the base branch from speedup-amax-kernel to dev November 26, 2025 22:53
@matthiasdiener matthiasdiener changed the title Speedup amax triton [WIP] Speedup amax triton Nov 27, 2025
@matthiasdiener matthiasdiener changed the title [WIP] Speedup amax triton Current scaling: two-stage Triton amax kernel Dec 1, 2025
@matthiasdiener matthiasdiener marked this pull request as ready for review December 1, 2025 20:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants